Minutes, IBIS Quality Committee
11 December 2012
11:00-12:00 EST (08:00-09:00 PST)
ROLL CALL
Altera David Banas
Cadence Design Systems: * Joy Li
* Yingxin Sun
Cisco Systems: Tony Penaloza
Ericsson: Anders Ekholm
Green Streak Programs: Lynne Green
Huawei Technologies: Guan Tao
IBM: Bruce Archambeault
Greg Edlund
Intel * Michael Mirmak
IOMethodology: Lance Wang
Mentor Graphics: John Angulo
Micron Technology: Moshiul Haque,
Randy Wolff
Nokia Siemens Networks: Eckhard Lenski
QLogic Corp.: James Zhou
Signal Consulting Group: Tim Coyle
Signal Integrity Software * Mike LaBonte
Teraspeed Consulting Group: * Bob Ross
Texas Instruments: Pavani Jella
Everyone in attendance marked by *
NOTE: "AR" = Action Required.
-----------------------MINUTES ---------------------------
Mike LaBonte conducted the meeting.
Call for opens and IBIS related patent disclosures:
- None
AR Review:
- Joy and Yingxin work with Bob and Mike to possibly file parser bug
- Done, bug 140
New items:
Mike L showed bug 140:
- Bob: We did not know what to do with this bug
- We should demote combined non-monotonic warnings to a note
- There is no spec provision against it
- It would difficult to resolve
- Mike L: Notes are optional?
- Bob: No they are always printed
Mike L showed the IBISCHK messages slide in the presentation from Joy and Yingxin
- Mike L: The messages says they are non-mono, but they really are not
- Bob: With linear interpolation it is non-monotonic
- Michael M: That was the point of making the individual checks a NOTE
- Mike L: Should the warning be clarified, adding ", based on linear
interpolation"
- Michael M: It could be in a manual
- Bob: A parser spec could be
- Michael M: Do we want to separate spec checks from other checks?
- Bob: Bob Haller called it an error if it is an error 95% of the time
- In some buffers Vmeas can be outside Vinh and Vinl, for example
- Mike L: We should have a category reserved for spec violations
- The Vmeas check is not required by the spec
- Bob: The message number codes would not change
- Mike L: They are prefixed with letters E, W, etc.
Mike L showed the parser_history.txt document and the 2005 spec document:
- Mike L: We have only specified the changes to be made for each parser update
- The 2005 spec is not complete
- We have no full parser spec, but we seem to moving toward creating one
- Bob: I would not call it a spec
- The parser developer makes changes to it
- Mike L: I think we could write a complete spec
- Part of it would be how to use IBISCHK
- Part would be how to use the source code as a parser
- Michael M: We do need some kind of user manual
- For example someone complained that it didn't work on Windows 7
- They thought it would install something
- Bob: Three or four companies actually use it as a parser
- This would mostly be a manual
- Mike L: I could write an outline for a parser document
- Bob: It might not be organized by keyword the same as the 2005 document
- Mike L: Someone should write policies for what E, W, N, C mean
Michael M: Should we have a parser bug category for undocumented behaviors?
- People would report things they think the parser should do, but aren't sure
- This would become the queue of ideas and items to be implemented
- Mike L: Not sure it should be done with Mantis
- I will be showing a prototype wiki soon
AR: Mike attempt to create IQ report for DesignCON summit
AR: Mike create outline for new IBISCHK specification
AR: Bob define policies for ERROR, WARNING, CAUTION, NOTE categories
Review of group meeting schedule:
- We agreed the next meeting would be Jan 8
Next meetings:
- The next two meetings will be Jan 8 and Jan 22
- The meeting ended at 11:09 ET